|
|
|
|
|
|
|
Welcome to Object-Oriented Programming with Visual Basic |
|
|
|
|
|
|
|
|
Greetings, fellow developer. Over the next twenty-one days, you will learn how to effectively implement object-oriented programming in Visual Basic. Along the way, you will examine a great deal of sample code, including fully functional classes, subsystems, and components. These structures will help you develop reusable applications much more quickly than if you had to start from scratch. The lessons on design patterns will also help you develop extensible application architectures so that constructing complete applications is as simple as plugging in subsystems with their interdependencies already mapped out in terms of methods calling methods. |
|
|
|
|
|
|
|
|
The lessons start out with the basics of object-oriented programming. They then progress to a relatively straightforward treatment of more complex concepts. After that, the chapters cover in detail the actual subsystems commonly usedand reusedin many Visual Basic applications. |
|
|
|
|
|
|
|
|
Who Should Read This Book |
|
|
|
|
|
|
|
|
Any Visual Basic developer who needs to quickly learn how to implement the powerful object-oriented programming paradigm in Visual Basic should definitely read this book. Pay close attention to each lesson because object-oriented programming is complex, although not impossible to learn. Developers who have some knowledge of modularization of code and information hiding will progress through the lessons pretty quickly. If you're new to programming in general, I strongly advise that you give serious attention to the lessons in the first week. Although this book is certainly geared towards Visual Basic developers, developers in other languages such as Java, Visual C++, PowerBuilder, and Delphi can also benefit from the treatment of subsystems, classes, and design patterns because these structures are universal for all programming languages. |
|
|
|
|
|
|
|
|
Why You Need to Use This Book |
|
|
|
|
|
|
|
|
If you've developed Visual Basic applications for a while, you might have developed applications very quickly by placing code in forms and maybe one or two code modules. This works fine on one project, but as soon as you started another project, you might |
|
|
|
|
|